home *** CD-ROM | disk | FTP | other *** search
- =======================================================================
- NotesSQL 3.01a
- an ODBC Driver for Domino
- =======================================================================
- Licensed Materials - Property of Lotus and/or IBM
- (c) Copyright Lotus Development Corporation 1999 - 2001
- (c) Copyright IBM Corporation.
- All rights reserved.
- US Government Users Restricted Rights - Use, duplication or disclosure
- restricted by GSA ADP Schedule Contract with Lotus and/or IBM Corp.
-
- Lotus is a registered trademark of Lotus and/or IBM.
-
- January 2002
-
- For up-to-date product information, see http://www.lotus.com/notessql.
-
-
- ---------
- Contents:
- ---------
- 1. Installation Requirements and Details
- 2. Files Installed
- 3. Changes Since Release 3.01
- 4. Known Issues
- 5. Resolved Issues
-
- ----------------------------------------
- 1. Installation Requirements and Details
- ----------------------------------------
-
- To install and use NotesSQL, you need:
-
- - An ODBC Driver Manager version 3.0 or later
- - One of the following:
- - Microsoft Windows 95, 98, or 2000
- - Microsoft Windows NT 4.0 or later with Service
- Pack 4 or later
- - One of the following, with a full user license:
- - Lotus Notes Client release 4.6.4 or later
- - Lotus Domino release 4.6.4 or later
- - Lotus Notes Designer release 4.6.4 or later
- - Lotus Domino Off-Line Services release 1.01 or later
-
- For client-based third-party applications, NotesSQL and the Designer or
- Desktop software must be installed on your local machine. For
- server-based applications (for example, Microsoft Internet Information
- Server), NotesSQL and any one of the versions above must be installed
- on the server.
-
- Installation details:
-
- This version of NotesSQL should have been installed automatically when
- you ran the self-executing installation file for your platform from the
- NotesSQL Web page. If you need to reinstall NotesSQL, see "Installing
- NotesSQL" in the documentation.
-
- The installation program checks for previous versions of the NotesSQL
- driver files and renames them to "*.30x" (where "x" is the specific
- version digit; for example, "nsql32.300"). In the unlikely event that
- you need to use an earlier version of NotesSQL after installing version
- 3.01a, do the following:
- - To restore NotesSQL 3.0 or 3.01 driver files, simply rename the driver
- DLLs that were backed up during the installation of NotesSQL 3.01a. The
- 3.0 driver files will have the extension "*.300" in the NotesSQL
- directory; 3.01 driver files will have a "*.301" extension. Rename the
- appropriate files to "*.dll". Your machine Data Sources will now use
- the old version of NotesSQL.
-
- Note: We suggest that you back up your 3.01a files before restoring the
- older drive files.
-
-
- ------------------
- 2. Files Installed
- ------------------
- <Installation directory> // These files (including the DOCS directory
- index.htm // and its contents) may be in an earlier
- notessql.nsf // NotesSQL installation directory.
- nsql301.log
- NSQL32.dll
- NSQLC32.dll
- NSQLV32.dll
- NSQLE32.exe
- license.txt
- Nsql_ALM.exe
- nsql_alm.GID
- nsql_alm.hlp
- Readme.txt
- UninDrv.dll
- <Docs>
- HTML and GIF files
- <License>
- Multilingual license files
-
- <\Windows\system>
- CTL3D32.DLL // If not already installed
- DS16GT.DLL
- DS32GT.DLL
- MSCPXL32.DLL
- MTXDM.DLL
- ODBC16GT.DLL
- ODBC32GT.DLL
- ODBC32.DLL
- ODBCAD32.EXE
- ODBCCP32.CPL
- ODBCCP32.DLL
- ODBCCR32.DLL
- ODBCINT.DLL
- ODBCTRAC.DLL
- MSVCRT40.DLL
-
-
- -----------------------------
- 3. Changes since release 3.01
- -----------------------------
- See "Resolved Issues"
-
-
- ---------------
- 4. Known Issues
- ---------------
-
- We are investigating the following problems and hope to fix them in a
- future release.
-
- - You cannot currently use the NotesSQL ODBC dialogs in the ODBC
- Data Source Administrator to rename a file DSN. Instead, you must
- rename the file manually or delete the file and recreate it with a
- different name.
- - You may be unable to use a DSN to open a database on a remote AIX
- server if, while using the NotesSQL ODBC dialogs to create the DSN,
- you typed the database name (instead of selecting it from the list
- of databases on the server) and omitted the .NSF extension.
- - In some circumstances, you may not be able to access .nsf files in
- subdirectories off of the Notes/Data directory on AS/400 Domino
- Server.
- - During NotesSQL configuration or at application run time, you may
- sometimes be prompted for the password of the current user, rather
- than the password for the user (if any) specified in a DSN or an
- ODBC connection call. This is because NotesSQL needs to access a
- server to build a list of available databases. Specifically, you
- may encounter this prompt in the following circumstances:
-
- - During NotesSQL configuration: While using the NotesSQL ODBC setup
- dialogs to create or modify a DSN that specifies a database on a
- server
- - At application run time: As the result of a call to
- SQLDriverConnect or SQLBrowseConnect that attempts to connect to
- a database on a server
-
- In either situation, supply the password for the current user (the
- user whose Notes ID is listed in the local notes.ini file). This
- allows NotesSQL to access the server and build the list of available
- databases.
-
- (Note that you may still receive an additional password prompt
- during a connection attempt. This is normal behavior that is part of
- the Notes security model, and depends entirely on the correctness
- of any user name and password information you supplied for the
- connection.)
- - Users of Lotus 1-2-3 Millenium Edition may experience
- problems when using the Query Table Assistant (Create - Database -
- Query Table) to access external tables. To avoid these problems,
- first select File - Addins - Manage Addins and make sure the
- dqaui.12a addin is checked. Then use the Query menu, instead of the
- Query Table Assistant, to make queries.
- - You may encounter problems editing the names of user and system DSNs
- if you have an incorrect version of the ODBC driver manager loaded.
- To avoid this problem, make sure you install the version provided
- with NotesSQL 3.0 or 3.01.
- - If you create an empty table (a table that has no fields) and you
- attempt this SQL statement against that table (represented here by
- "T1"):
-
- select *, NoteID from T1
-
- a crash occurs.
-
- Workaround:
- Use any of the following statements to prevent the crash:
-
- select NoteID, * from T1
- select * from T1
- select NoteID from T1
-
- - User cannot authenticate when Local DB with Enforce Consistant ACL,
- and user is member of a group.
- If you:
- 1. Create a new blank database Locally
- 2. Add a view and form
- 3. Add a group you are a member of to the ACL with Manager Access
- 4. Removed your Hierarchical name from the ACL
- 5. Set default to No Access
- 6. Turn on Enforce Consistent ACL
- 7. Add a DSN to this Local DB
- 8. Try to connect to this db using ODBC Test
- You will receive an error that the user is not authenticated. The
- reason for this is that we are using the function NSFBuildNamesList
- for authentication, and this function will not authenticate a username
- in a local database against a server group (list of names).
- Workaround: add the hierarchical names of the users that need access
- to the individual database to its ACL.
-
- - Under some conditions, for example using ODBC test, the following
- scenario may occur:
- 1. If you try to connect to a database but the connection fails to
- occur through the DSN (for example, if the database doesn't exist
- or if the database is on a server that is down), you should get
- the error "[lotus][odbc lotus notes]file does not exist."
- 2. Click OK to clear the error dialog.
- 3. Now a bit of lag time may occur before control is returned to the
- application, especially on slower machines, because NotesSQL is
- still performing some processing. If you try to execute another
- statement or close ODBC test during this period, a crash occurs:
- The instruction at "0x1f7d8006" referenced memory at
- "0x00000035". The memory could not be "written".
- Workaround: wait for control to be returned to the application before
- attempting to execute another statement or close the application.
-
-
- ------------------
- 5. Resolved Issues
- ------------------
- NotesSQL 3.01a is a hotfix to address the issue with multiple user
- credentials in one instance of NotesSQL (SPR #RWIS4XVNHD). This fix
- requires the addition of the file NSQLE32.exe, installed into the
- NotesSQL directory.